←Back to abhikr.com Discuss this work
Draft. Not for publishing yet
Metrics and delivery detail come from your notes. The measurement method behind the accessibility figure isn't confirmed yet - see “What’s still open” below.
Turn off the Draft notice tweak once you’ve been through it.

A parcel-tracking app that needed dependable status visibility and accessible interaction, with accessibility maturity starting near 10%. Three months on-site with the customer in Sweden, running PI Planning and delivery alongside the engineering work.

{{ m.k }}
{{ m.v }}

On top of the accessibility gap, the app runs on Compose over an existing view hierarchy, so a fix in one layer had to interoperate cleanly with the other. Working alongside the customer on-site in Sweden meant the plan and the roadmap were shared in real time through PI Planning, not handed over after the fact.

Outcome

Accessibility, from a gap to the default.

Before ~10%
After ~90%

Verified with manual and automated testing. The Customs Status module shipped in a single PR release, zero-defect.

{{ p.n }}

{{ p.title }}

{{ t }}

{{ p.body }}

What’s still open

Everything above is stated as given. This one isn't confirmed yet.

{{ g.item }}
{{ g.ask }}

Got an accessibility gap to close?

TalkBack audits, Compose/XML interop, and the CI gates that keep a fix from regressing.

Start a conversation
← Back to abhikr.com
© 2026 Abhishek Kumar · abhikr.com